Default Playback Device Designation

ABSTRACT

Systems and methods discussed herein involve designating a default playback device in a local playback network. One method may involve determining that a networked microphone device is available for assignment to one or more playback zones within a local playback network, displaying a prompt to indicate at least one playback zone to which the network microphone device is to be assigned, receiving an input indicating a particular playback zone in the local playback system to which the network microphone device is to be assigned, and storing data indicating an assignment of the network microphone device to the particular playback zone.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S.application Ser. No. 15/098,867 entitled “Default Playback DeviceDesignation” filed on Apr. 14, 2016 and claims the benefit of priorityunder 35 USC § 119(e) to U.S. Provisional Application Ser. No.62/298,410 filed on Feb. 22, 2016 and entitled “DEFAULT PLAYBACKDEVICE(S)”, U.S. Provisional Application Ser. No. 62/298,418 filed onFeb. 22, 2016 and entitled “AUDIO RESPONSE PLAYBACK”, U.S. ProvisionalApplication Ser. No. 62/298,433 filed on Feb. 22, 2016 and entitled“ROOM-CORRECTED VOICE DETECTION”, U.S. Provisional Application Ser. No.62/298,439 filed on Feb. 22, 2016 and entitled “CONTENT MIXING”, U.S.Provisional Application Ser. No. 62/298,425 filed on Feb. 22, 2016 andentitled “MUSIC SERVICE SELECTION”, U.S. Provisional Application Ser.No. 62/298,350 filed on Feb. 22, 2016 and entitled “METADATA EXCHANGEINVOLVING A NETWORKED PLAYBACK SYSTEM AND A NETWORKED MICROPHONESYSTEM”, U.S. Provisional Application Ser. No. 62/298,388 filed on Feb.22, 2016 and entitled “HANDLING OF LOSS OF PAIRING BETWEEN NETWORKEDDEVICES”, U.S. Provisional Application Ser. No. 62/298,393 filed on Feb.22, 2016 and entitled “ACTION BASED ON USER ID”, U.S. ProvisionalApplication Ser. No. 62/312,350 filed on Mar. 23, 2016 and entitled“VOICE CONTROL OF A MEDIA PLAYBACK SYSTEM”, the contents each of whichare herein incorporated by reference in their entireties.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other elementsdirected to media playback or some aspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loudsetting were limited until in 2003, when SONOS, Inc. filed for one ofits first patent applications, entitled “Method for Synchronizing AudioPlayback between Multiple Networked Devices,” and began offering a mediaplayback system for sale in 2005. The Sonos Wireless HiFi System enablespeople to experience music from many sources via one or more networkedplayback devices. Through a software control application installed on asmartphone, tablet, or computer, one can play what he or she wants inany room that has a networked playback device. Additionally, using thecontroller, for example, different songs can be streamed to each roomwith a playback device, rooms can be grouped together for synchronousplayback, or the same song can be heard in all rooms synchronously.

Given the ever growing interest in digital media, there continues to bea need to develop consumer-accessible technologies to further enhancethe listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example media playback system configuration in whichcertain embodiments may be practiced;

FIG. 2 shows a functional block diagram of an example playback device;

FIG. 3 shows a functional block diagram of an example control device;

FIG. 4 shows an example controller interface;

FIG. 5 shows an illustrative example of a plurality of network-capabledevices;

FIG. 6 shows a functional block diagram of an example network microphonedevice;

FIG. 7 shows an example flow diagram for designating default playbackdevice(s);

FIG. 8A-D show example user interfaces for assigning network microphonedevices; and

FIG. 9 shows an example flow diagram for applying default playbackdevice designation(s).

The drawings are for the purpose of illustrating example embodiments,but it is understood that the inventions are not limited to thearrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Some embodiments described herein involve designating a default playbackdevice in a media playback system and applying such designation of thedefault playback device. In one embodiment, a network microphone device(“NMD”) may be assigned to a playback zone in a media playback system.In such a case, one or more of the playback devices in the playback zonemay be designated as the default playback device for the NMD. Someexamples herein involve methods and processes for designating thedefault playback device and/or assigning the NMD to a playback zone.Other examples involve methods and processes for causing the defaultplayback device to take certain actions. In an embodiment, a command viathe NMD to cause the media playback system to perform a particularplayback command may not identify a specific playback zone. In such acase, the default playback device may be identified based on theassignment of the NMD to the playback zone of the default playbackdevice. The default playback device may accordingly perform theparticular playback command. Other scenarios and examples involving thedesignation of default playback devices and application of suchdesignations can be found in the following sections.

As indicated above, the examples provided herein involve designating adefault playback device in a media playback system and applying suchdesignation of the default playback device. In one aspect, a method isprovided. The method involves determining, by a computing device, that anetworked microphone device is available for assignment to one or moreplayback zones within a local playback network, displaying by thecomputing device, a prompt to indicate at least one playback zone towhich the network microphone device is to be assigned, receiving, by thecomputing device, an input indicating a particular playback zone in thelocal playback network to which the network microphone device is to beassigned, and storing, by the computing device, data indicating anassignment of the network microphone device to the particular playbackzone.

In another aspect, a computing device is provided. The computing deviceincludes a processor, and memory having stored thereon instructionsexecutable by the processor to cause the device to perform functions.The functions include determining that a networked microphone device isavailable for assignment to one or more playback zones within a localplayback network, displaying a prompt to indicate at least one playbackzone to which the network microphone device is to be assigned, receivingan input indicating a particular playback zone in the local playbacknetwork to which the network microphone device is to be assigned, andstoring data indicating an assignment of the network microphone deviceto the particular playback zone.

In yet another aspect, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions. The functions include determining that anetworked microphone device is available for assignment to one or moreplayback zones within a local playback network, displaying a prompt toindicate at least one playback zone to which the network microphonedevice is to be assigned, receiving an input indicating a particularplayback zone in the local playback network to which the networkmicrophone device is to be assigned, and storing data indicating anassignment of the network microphone device to the particular playbackzone.

In one aspect, a method is provided. The method maintaining, by acomputing device, a database comprising data indicating an assignment ofan identification of a network microphone device to a playback zone of amedia playback system, receiving, by the computing device, a messageindicating (i) the identification of the network microphone device and(ii) a media playback command, identifying, by the computing device theplayback zone in the media playback system based on the data in thedatabase and the received message, and transmitting, by the computingdevice to the playback zone, a message indicating the media playbackcommand.

In another aspect, a computing device is provided. The computing deviceincludes a processor, and memory having stored thereon instructionsexecutable by the processor to cause the device to perform functions.The functions include maintaining a database comprising data indicatingan assignment of an identification of a network microphone device to aplayback zone of a media playback system, receiving a message indicating(i) the identification of the network microphone device and (ii) a mediaplayback command, identifying the playback zone in the media playbacksystem based on the data in the database and the received message, andtransmitting to the playback zone, a message indicating the mediaplayback command.

In yet another aspect, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions. The functions include maintaining adatabase comprising data indicating an assignment of an identificationof a network microphone device to a playback zone of a media playbacksystem, receiving a message indicating (i) the identification of thenetwork microphone device and (ii) a media playback command, identifyingthe playback zone in the media playback system based on the data in thedatabase and the received message, and transmitting to the playbackzone, a message indicating the media playback command.

While some examples described herein may refer to functions performed bygiven actors such as “users” and/or other entities, it should beunderstood that this is for purposes of explanation only. The claimsshould not be interpreted to require action by any such example actorunless explicitly required by the language of the claims themselves. Itwill be understood by one of ordinary skill in the art that thisdisclosure includes numerous other embodiments.

II. Example Operating Environment

FIG. 1 shows an example configuration of a media playback system 100 inwhich one or more embodiments disclosed herein may be practiced orimplemented. The media playback system 100 as shown is associated withan example home environment having several rooms and spaces, such as forexample, a master bedroom, an office, a dining room, and a living room.As shown in the example of FIG. 1, the media playback system 100includes playback devices 102-124, control devices 126 and 128, and awired or wireless network router 130.

Further discussions relating to the different components of the examplemedia playback system 100 and how the different components may interactto provide a user with a media experience may be found in the followingsections. While discussions herein may generally refer to the examplemedia playback system 100, technologies described herein are not limitedto applications within, among other things, the home environment asshown in FIG. 1. For instance, the technologies described herein may beuseful in environments where multi-zone audio may be desired, such as,for example, a commercial setting like a restaurant, mall or airport, avehicle like a sports utility vehicle (SUV), bus or car, a ship or boat,an airplane, and so on.

a. Example Playback Devices

FIG. 2 shows a functional block diagram of an example playback device200 that may be configured to be one or more of the playback devices102-124 of the media playback system 100 of FIG. 1. The playback device200 may include a processor 202, software components 204, memory 206,audio processing components 208, audio amplifier(s) 210, speaker(s) 212,a network interface 214 including wireless interface(s) 216 and wiredinterface(s) 218, and microphone(s) 220. In one case, the playbackdevice 200 may not include the speaker(s) 212, but rather a speakerinterface for connecting the playback device 200 to external speakers.In another case, the playback device 200 may include neither thespeaker(s) 212 nor the audio amplifier(s) 210, but rather an audiointerface for connecting the playback device 200 to an external audioamplifier or audio-visual receiver.

In one example, the processor 202 may be a clock-driven computingcomponent configured to process input data according to instructionsstored in the memory 206. The memory 206 may be a tangiblecomputer-readable medium configured to store instructions executable bythe processor 202. For instance, the memory 206 may be data storage thatcan be loaded with one or more of the software components 204 executableby the processor 202 to achieve certain functions. In one example, thefunctions may involve the playback device 200 retrieving audio data froman audio source or another playback device. In another example, thefunctions may involve the playback device 200 sending audio data toanother device or playback device on a network. In yet another example,the functions may involve pairing of the playback device 200 with one ormore playback devices to create a multi-channel audio environment.

Certain functions may involve the playback device 200 synchronizingplayback of audio content with one or more other playback devices.During synchronous playback, a listener will preferably not be able toperceive time-delay differences between playback of the audio content bythe playback device 200 and the one or more other playback devices. U.S.Pat. No. 8,234,395 entitled, “System and method for synchronizingoperations among a plurality of independently clocked digital dataprocessing devices,” which is hereby incorporated by reference, providesin more detail some examples for audio playback synchronization amongplayback devices.

The memory 206 may further be configured to store data associated withthe playback device 200, such as one or more zones and/or zone groupsthe playback device 200 is a part of, audio sources accessible by theplayback device 200, or a playback queue that the playback device 200(or some other playback device) may be associated with. The data may bestored as one or more state variables that are periodically updated andused to describe the state of the playback device 200. The memory 206may also include the data associated with the state of the other devicesof the media system, and shared from time to time among the devices sothat one or more of the devices have the most recent data associatedwith the system. Other embodiments are also possible.

The audio processing components 208 may include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor (DSP), and soon. In one embodiment, one or more of the audio processing components208 may be a subcomponent of the processor 202. In one example, audiocontent may be processed and/or intentionally altered by the audioprocessing components 208 to produce audio signals. The produced audiosignals may then be provided to the audio amplifier(s) 210 foramplification and playback through speaker(s) 212. Particularly, theaudio amplifier(s) 210 may include devices configured to amplify audiosignals to a level for driving one or more of the speakers 212. Thespeaker(s) 212 may include an individual transducer (e.g., a “driver”)or a complete speaker system involving an enclosure with one or moredrivers. A particular driver of the speaker(s) 212 may include, forexample, a subwoofer (e.g., for low frequencies), a mid-range driver(e.g., for middle frequencies), and/or a tweeter (e.g., for highfrequencies). In some cases, each transducer in the one or more speakers212 may be driven by an individual corresponding audio amplifier of theaudio amplifier(s) 210. In addition to producing analog signals forplayback by the playback device 200, the audio processing components 208may be configured to process audio content to be sent to one or moreother playback devices for playback.

Audio content to be processed and/or played back by the playback device200 may be received from an external source, such as via an audioline-in input connection (e.g., an auto-detecting 3.5 mm audio line-inconnection) or the network interface 214.

The network interface 214 may be configured to facilitate a data flowbetween the playback device 200 and one or more other devices on a datanetwork. As such, the playback device 200 may be configured to receiveaudio content over the data network from one or more other playbackdevices in communication with the playback device 200, network deviceswithin a local area network, or audio content sources over a wide areanetwork such as the Internet. In one example, the audio content andother signals transmitted and received by the playback device 200 may betransmitted in the form of digital packet data containing an InternetProtocol (IP)-based source address and IP-based destination addresses.In such a case, the network interface 214 may be configured to parse thedigital packet data such that the data destined for the playback device200 is properly received and processed by the playback device 200.

As shown, the network interface 214 may include wireless interface(s)216 and wired interface(s) 218. The wireless interface(s) 216 mayprovide network interface functions for the playback device 200 towirelessly communicate with other devices (e.g., other playbackdevice(s), speaker(s), receiver(s), network device(s), control device(s)within a data network the playback device 200 is associated with) inaccordance with a communication protocol (e.g., any wireless standardincluding IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4Gmobile communication standard, and so on). The wired interface(s) 218may provide network interface functions for the playback device 200 tocommunicate over a wired connection with other devices in accordancewith a communication protocol (e.g., IEEE 802.3). While the networkinterface 214 shown in FIG. 2 includes both wireless interface(s) 216and wired interface(s) 218, the network interface 214 may in someembodiments include only wireless interface(s) or only wiredinterface(s).

The microphone(s) 220 may be arranged to detect sound in the environmentof the playback device 200. For instance, the microphone(s) may bemounted on an exterior wall of a housing of the playback device. Themicrophone(s) may be any type of microphone now known or later developedsuch as a condenser microphone, electret condenser microphone, or adynamic microphone. The microphone(s) may be sensitive to a portion ofthe frequency range of the speaker(s) 220. One or more of the speaker(s)220 may operate in reverse as the microphone(s) 220. In some aspects,the playback device 200 might not have microphone(s) 220.

In one example, the playback device 200 and one other playback devicemay be paired to play two separate audio components of audio content.For instance, playback device 200 may be configured to play a leftchannel audio component, while the other playback device may beconfigured to play a right channel audio component, thereby producing orenhancing a stereo effect of the audio content. The paired playbackdevices (also referred to as “bonded playback devices”) may further playaudio content in synchrony with other playback devices.

In another example, the playback device 200 may be sonicallyconsolidated with one or more other playback devices to form a single,consolidated playback device. A consolidated playback device may beconfigured to process and reproduce sound differently than anunconsolidated playback device or playback devices that are paired,because a consolidated playback device may have additional speakerdrivers through which audio content may be rendered. For instance, ifthe playback device 200 is a playback device designed to render lowfrequency range audio content (i.e. a subwoofer), the playback device200 may be consolidated with a playback device designed to render fullfrequency range audio content. In such a case, the full frequency rangeplayback device, when consolidated with the low frequency playbackdevice 200, may be configured to render only the mid and high frequencycomponents of audio content, while the low frequency range playbackdevice 200 renders the low frequency component of the audio content. Theconsolidated playback device may further be paired with a singleplayback device or yet another consolidated playback device.

By way of illustration, SONOS, Inc. presently offers (or has offered)for sale certain playback devices including a “PLAY:1,” “PLAY:3,”“PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any otherpast, present, and/or future playback devices may additionally oralternatively be used to implement the playback devices of exampleembodiments disclosed herein. Additionally, it is understood that aplayback device is not limited to the example illustrated in FIG. 2 orto the SONOS product offerings. For example, a playback device mayinclude a wired or wireless headphone. In another example, a playbackdevice may include or interact with a docking station for personalmobile media playback devices. In yet another example, a playback devicemay be integral to another device or component such as a television, alighting fixture, or some other device for indoor or outdoor use.

b. Example Playback Zone Configurations

Referring back to the media playback system 100 of FIG. 1, theenvironment may have one or more playback zones, each with one or moreplayback devices. The media playback system 100 may be established withone or more playback zones, after which one or more zones may be added,or removed to arrive at the example configuration shown in FIG. 1. Eachzone may be given a name according to a different room or space such asan office, bathroom, master bedroom, bedroom, kitchen, dining room,living room, and/or balcony. In one case, a single playback zone mayinclude multiple rooms or spaces. In another case, a single room orspace may include multiple playback zones.

As shown in FIG. 1, the balcony, dining room, kitchen, bathroom, office,and bedroom zones each have one playback device, while the living roomand master bedroom zones each have multiple playback devices. In theliving room zone, playback devices 104, 106, 108, and 110 may beconfigured to play audio content in synchrony as individual playbackdevices, as one or more bonded playback devices, as one or moreconsolidated playback devices, or any combination thereof. Similarly, inthe case of the master bedroom, playback devices 122 and 124 may beconfigured to play audio content in synchrony as individual playbackdevices, as a bonded playback device, or as a consolidated playbackdevice.

In one example, one or more playback zones in the environment of FIG. 1may each be playing different audio content. For instance, the user maybe grilling in the balcony zone and listening to hip hop music beingplayed by the playback device 102 while another user may be preparingfood in the kitchen zone and listening to classical music being playedby the playback device 114. In another example, a playback zone may playthe same audio content in synchrony with another playback zone. Forinstance, the user may be in the office zone where the playback device118 is playing the same rock music that is being playing by playbackdevice 102 in the balcony zone. In such a case, playback devices 102 and118 may be playing the rock music in synchrony such that the user mayseamlessly (or at least substantially seamlessly) enjoy the audiocontent that is being played out-loud while moving between differentplayback zones. Synchronization among playback zones may be achieved ina manner similar to that of synchronization among playback devices, asdescribed in previously referenced U.S. Pat. No. 8,234,395.

As suggested above, the zone configurations of the media playback system100 may be dynamically modified, and in some embodiments, the mediaplayback system 100 supports numerous configurations. For instance, if auser physically moves one or more playback devices to or from a zone,the media playback system 100 may be reconfigured to accommodate thechange(s). For instance, if the user physically moves the playbackdevice 102 from the balcony zone to the office zone, the office zone maynow include both the playback device 118 and the playback device 102.The playback device 102 may be paired or grouped with the office zoneand/or renamed if so desired via a control device such as the controldevices 126 and 128. On the other hand, if the one or more playbackdevices are moved to a particular area in the home environment that isnot already a playback zone, a new playback zone may be created for theparticular area.

Further, different playback zones of the media playback system 100 maybe dynamically combined into zone groups or split up into individualplayback zones. For instance, the dining room zone and the kitchen zone114 may be combined into a zone group for a dinner party such thatplayback devices 112 and 114 may render audio content in synchrony. Onthe other hand, the living room zone may be split into a television zoneincluding playback device 104, and a listening zone including playbackdevices 106, 108, and 110, if the user wishes to listen to music in theliving room space while another user wishes to watch television.

c. Example Control Devices

FIG. 3 shows a functional block diagram of an example control device 300that may be configured to be one or both of the control devices 126 and128 of the media playback system 100. As shown, the control device 300may include a processor 302, memory 304, a network interface 306, a userinterface 308, microphone(s) 310, and software components 312. In oneexample, the control device 300 may be a dedicated controller for themedia playback system 100. In another example, the control device 300may be a network device on which media playback system controllerapplication software may be installed, such as for example, an iPhone™,iPad™ or any other smart phone, tablet or network device (e.g., anetworked computer such as a PC or Mac™).

The processor 302 may be configured to perform functions relevant tofacilitating user access, control, and configuration of the mediaplayback system 100. The memory 304 may be data storage that can beloaded with one or more of the software components executable by theprocessor 302 to perform those functions. The memory 304 may also beconfigured to store the media playback system controller applicationsoftware and other data associated with the media playback system 100and the user.

In one example, the network interface 306 may be based on an industrystandard (e.g., infrared, radio, wired standards including IEEE 802.3,wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n,802.11ac, 802.15, 4G mobile communication standard, and so on). Thenetwork interface 306 may provide a means for the control device 300 tocommunicate with other devices in the media playback system 100. In oneexample, data and information (e.g., such as a state variable) may becommunicated between control device 300 and other devices via thenetwork interface 306. For instance, playback zone and zone groupconfigurations in the media playback system 100 may be received by thecontrol device 300 from a playback device or another network device, ortransmitted by the control device 300 to another playback device ornetwork device via the network interface 306. In some cases, the othernetwork device may be another control device.

Playback device control commands such as volume control and audioplayback control may also be communicated from the control device 300 toa playback device via the network interface 306. As suggested above,changes to configurations of the media playback system 100 may also beperformed by a user using the control device 300. The configurationchanges may include adding/removing one or more playback devices to/froma zone, adding/removing one or more zones to/from a zone group, forminga bonded or consolidated player, separating one or more playback devicesfrom a bonded or consolidated player, among others. Accordingly, thecontrol device 300 may sometimes be referred to as a controller, whetherthe control device 300 is a dedicated controller or a network device onwhich media playback system controller application software isinstalled.

Control device 300 may include microphone(s) 310. Microphone(s) 310 maybe arranged to detect sound in the environment of the control device300. Microphone(s) 310 may be any type of microphone now known or laterdeveloped such as a condenser microphone, electret condenser microphone,or a dynamic microphone. The microphone(s) may be sensitive to a portionof a frequency range. Two or more microphones 310 may be arranged tocapture location information of an audio source (e.g., voice, audiblesound) and/or to assist in filtering background noise.

The user interface 308 of the control device 300 may be configured tofacilitate user access and control of the media playback system 100, byproviding a controller interface such as the controller interface 400shown in FIG. 4. The controller interface 400 includes a playbackcontrol region 410, a playback zone region 420, a playback status region430, a playback queue region 440, and an audio content sources region450. The user interface 400 as shown is just one example of a userinterface that may be provided on a network device such as the controldevice 300 of FIG. 3 (and/or the control devices 126 and 128 of FIG. 1)and accessed by users to control a media playback system such as themedia playback system 100. Other user interfaces of varying formats,styles, and interactive sequences may alternatively be implemented onone or more network devices to provide comparable control access to amedia playback system.

The playback control region 410 may include selectable (e.g., by way oftouch or by using a cursor) icons to cause playback devices in aselected playback zone or zone group to play or pause, fast forward,rewind, skip to next, skip to previous, enter/exit shuffle mode,enter/exit repeat mode, enter/exit cross fade mode. The playback controlregion 410 may also include selectable icons to modify equalizationsettings, and playback volume, among other possibilities.

The playback zone region 420 may include representations of playbackzones within the media playback system 100. In some embodiments, thegraphical representations of playback zones may be selectable to bringup additional selectable icons to manage or configure the playback zonesin the media playback system, such as a creation of bonded zones,creation of zone groups, separation of zone groups, and renaming of zonegroups, among other possibilities.

For example, as shown, a “group” icon may be provided within each of thegraphical representations of playback zones. The “group” icon providedwithin a graphical representation of a particular zone may be selectableto bring up options to select one or more other zones in the mediaplayback system to be grouped with the particular zone. Once grouped,playback devices in the zones that have been grouped with the particularzone will be configured to play audio content in synchrony with theplayback device(s) in the particular zone. Analogously, a “group” iconmay be provided within a graphical representation of a zone group. Inthis case, the “group” icon may be selectable to bring up options todeselect one or more zones in the zone group to be removed from the zonegroup. Other interactions and implementations for grouping andungrouping zones via a user interface such as the user interface 400 arealso possible. The representations of playback zones in the playbackzone region 420 may be dynamically updated as playback zone or zonegroup configurations are modified.

The playback status region 430 may include graphical representations ofaudio content that is presently being played, previously played, orscheduled to play next in the selected playback zone or zone group. Theselected playback zone or zone group may be visually distinguished onthe user interface, such as within the playback zone region 420 and/orthe playback status region 430. The graphical representations mayinclude track title, artist name, album name, album year, track length,and other relevant information that may be useful for the user to knowwhen controlling the media playback system via the user interface 400.

The playback queue region 440 may include graphical representations ofaudio content in a playback queue associated with the selected playbackzone or zone group. In some embodiments, each playback zone or zonegroup may be associated with a playback queue containing informationcorresponding to zero or more audio items for playback by the playbackzone or zone group. For instance, each audio item in the playback queuemay comprise a uniform resource identifier (URI), a uniform resourcelocator (URL) or some other identifier that may be used by a playbackdevice in the playback zone or zone group to find and/or retrieve theaudio item from a local audio content source or a networked audiocontent source, possibly for playback by the playback device.

In one example, a playlist may be added to a playback queue, in whichcase information corresponding to each audio item in the playlist may beadded to the playback queue. In another example, audio items in aplayback queue may be saved as a playlist. In a further example, aplayback queue may be empty, or populated but “not in use” when theplayback zone or zone group is playing continuously streaming audiocontent, such as Internet radio that may continue to play untilotherwise stopped, rather than discrete audio items that have playbackdurations. In an alternative embodiment, a playback queue can includeInternet radio and/or other streaming audio content items and be “inuse” when the playback zone or zone group is playing those items. Otherexamples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,”playback queues associated with the affected playback zones or zonegroups may be cleared or re-associated. For example, if a first playbackzone including a first playback queue is grouped with a second playbackzone including a second playback queue, the established zone group mayhave an associated playback queue that is initially empty, that containsaudio items from the first playback queue (such as if the secondplayback zone was added to the first playback zone), that contains audioitems from the second playback queue (such as if the first playback zonewas added to the second playback zone), or a combination of audio itemsfrom both the first and second playback queues. Subsequently, if theestablished zone group is ungrouped, the resulting first playback zonemay be re-associated with the previous first playback queue, or beassociated with a new playback queue that is empty or contains audioitems from the playback queue associated with the established zone groupbefore the established zone group was ungrouped. Similarly, theresulting second playback zone may be re-associated with the previoussecond playback queue, or be associated with a new playback queue thatis empty, or contains audio items from the playback queue associatedwith the established zone group before the established zone group wasungrouped. Other examples are also possible.

Referring back to the user interface 400 of FIG. 4, the graphicalrepresentations of audio content in the playback queue region 440 mayinclude track titles, artist names, track lengths, and other relevantinformation associated with the audio content in the playback queue. Inone example, graphical representations of audio content may beselectable to bring up additional selectable icons to manage and/ormanipulate the playback queue and/or audio content represented in theplayback queue. For instance, a represented audio content may be removedfrom the playback queue, moved to a different position within theplayback queue, or selected to be played immediately, or after anycurrently playing audio content, among other possibilities. A playbackqueue associated with a playback zone or zone group may be stored in amemory on one or more playback devices in the playback zone or zonegroup, on a playback device that is not in the playback zone or zonegroup, and/or some other designated device.

The audio content sources region 450 may include graphicalrepresentations of selectable audio content sources from which audiocontent may be retrieved and played by the selected playback zone orzone group. Discussions pertaining to audio content sources may be foundin the following section.

d. Example Audio Content Sources

As indicated previously, one or more playback devices in a zone or zonegroup may be configured to retrieve for playback audio content (e.g.according to a corresponding URI or URL for the audio content) from avariety of available audio content sources. In one example, audiocontent may be retrieved by a playback device directly from acorresponding audio content source (e.g., a line-in connection). Inanother example, audio content may be provided to a playback device overa network via one or more other playback devices or network devices.

Example audio content sources may include a memory of one or moreplayback devices in a media playback system such as the media playbacksystem 100 of FIG. 1, local music libraries on one or more networkdevices (such as a control device, a network-enabled personal computer,or a networked-attached storage (NAS), for example), streaming audioservices providing audio content via the Internet (e.g., the cloud), oraudio sources connected to the media playback system via a line-in inputconnection on a playback device or network devise, among otherpossibilities.

In some embodiments, audio content sources may be regularly added orremoved from a media playback system such as the media playback system100 of FIG. 1. In one example, an indexing of audio items may beperformed whenever one or more audio content sources are added, removedor updated. Indexing of audio items may involve scanning foridentifiable audio items in all folders/directory shared over a networkaccessible by playback devices in the media playback system, andgenerating or updating an audio content database containing metadata(e.g., title, artist, album, track length, among others) and otherassociated information, such as a URI or URL for each identifiable audioitem found. Other examples for managing and maintaining audio contentsources may also be possible.

The above discussions relating to playback devices, controller devices,playback zone configurations, and media content sources provide onlysome examples of operating environments within which functions andmethods described below may be implemented. Other operating environmentsand configurations of media playback systems, playback devices, andnetwork devices not explicitly described herein may also be applicableand suitable for implementation of the functions and methods.

e. Example Plurality of Networked Devices

FIG. 5 shows an example plurality of devices 500 that may be configuredto provide an audio playback experience based on voice control. Onehaving ordinary skill in the art will appreciate that the devices shownin FIG. 5 are for illustrative purposes only, and variations includingdifferent and/or additional devices may be possible. As shown, theplurality of devices 500 includes computing devices 504, 506, and 508;network microphone devices (NMDs) 512, 514, and 516; playback devices(PBDs) 532, 534, 536, and 538; and a controller device (CR) 522.

Each of the plurality of devices 500 may be network-capable devices thatcan establish communication with one or more other devices in theplurality of devices according to one or more network protocols, such asNFC, Bluetooth, Ethernet, and IEEE 802.11, among other examples, overone or more types of networks, such as wide area networks (WAN), localarea networks (LAN), and personal area networks (PAN), among otherpossibilities.

As shown, the computing devices 504, 506, and 508 may be part of a cloudnetwork 502. The cloud network 502 may include additional computingdevices. In one example, the computing devices 504, 506, and 508 may bedifferent servers. In another example, two or more of the computingdevices 504, 506, and 508 may be modules of a single server.Analogously, each of the computing device 504, 506, and 508 may includeone or more modules or servers. For ease of illustration purposesherein, each of the computing devices 504, 506, and 508 may beconfigured to perform particular functions within the cloud network 502.For instance, computing device 508 may be a source of audio content fora streaming music service.

As shown, the computing device 504 may be configured to interface withNMDs 512, 514, and 516 via communication path 542. NMDs 512, 514, and516 may be components of one or more “Smart Home” systems. In one case,NMDs 512, 514, and 516 may be physically distributed throughout ahousehold, similar to the distribution of devices shown in FIG. 1. Inanother case, two or more of the NMDs 512, 514, and 516 may bephysically positioned within relative close proximity of one another.Communication path 542 may comprise one or more types of networks, suchas a WAN including the Internet, LAN, and/or PAN, among otherpossibilities.

In one example, one or more of the NMDs 512, 514, and 516 may be devicesconfigured primarily for audio detection. In another example, one ormore of the NMDs 512, 514, and 516 may be components of devices havingvarious primary utilities. For instance, as discussed above inconnection to FIGS. 2 and 3, one or more of NMDs 512, 514, and 516 maybe the microphone(s) 220 of playback device 200 or the microphone(s) 310of network device 300. Further, in some cases, one or more of NMDs 512,514, and 516 may be the playback device 200 or network device 300. In anexample, one or more of NMDs 512, 514, and/or 516 may include multiplemicrophones arranged in a microphone array.

As shown, the computing device 506 may be configured to interface withCR 522 and PBDs 532, 534, 536, and 538 via communication path 544. Inone example, CR 522 may be a network device such as the network device200 of FIG. 2. Accordingly, CR 522 may be configured to provide thecontroller interface 400 of FIG. 4. Similarly, PBDs 532, 534, 536, and538 may be playback devices such as the playback device 300 of FIG. 3.As such, PBDs 532, 534, 536, and 538 may be physically distributedthroughout a household as shown in FIG. 1. For illustration purposes,PBDs 536 and 538 may be part of a bonded zone 530, while PBDs 532 and534 may be part of their own respective zones. As described above, thePBDs 532, 534, 536, and 538 may be dynamically bonded, grouped,unbonded, and ungrouped. Communication path 544 may comprise one or moretypes of networks, such as a WAN including the Internet, LAN, and/orPAN, among other possibilities.

In one example, as with NMDs 512, 514, and 516, CR 522 and PBDs 532,534, 536, and 538 may also be components of one or more “Smart Home”systems. In one case, PBDs 532, 534, 536, and 538 may be distributedthroughout the same household as the NMDs 512, 514, and 516. Further, assuggested above, one or more of PBDs 532, 534, 536, and 538 may be oneor more of NMDs 512, 514, and 516.

The NMDs 512, 514, and 516 may be part of a local area network, and thecommunication path 542 may include an access point that links the localarea network of the NMDs 512, 514, and 516 to the computing device 504over a WAN (communication path not shown). Likewise, each of the NMDs512, 514, and 516 may communicate with each other via such an accesspoint.

Similarly, CR 522 and PBDs 532, 534, 536, and 538 may be part of a localarea network and/or a local playback network as discussed in previoussections, and the communication path 544 may include an access pointthat links the local area network and/or local playback network of CR522 and PBDs 532, 534, 536, and 538 to the computing device 506 over aWAN. As such, each of the CR 522 and PBDs 532, 534, 536, and 538 mayalso communicate with each over such an access point.

In one example, communication paths 542 and 544 may comprise the sameaccess point. In an example, each of the NMDs 512, 514, and 516, CR 522,and PBDs 532, 534, 536, and 538 may access the cloud network 502 via thesame access point for a household.

As shown in FIG. 5, each of the NMDs 512, 514, and 516, CR 522, and PBDs532, 534, 536, and 538 may also directly communicate with one or more ofthe other devices via communication means 546. Communication means 546as described herein may involve one or more forms of communicationbetween the devices, according to one or more network protocols, overone or more types of networks, and/or may involve communication via oneor more other network devices. For instance, communication means 546 mayinclude one or more of for example, Bluetooth™ (IEEE 802.15), NFC,Wireless direct, and/or Proprietary wireless, among other possibilities.

In one example, CR 522 may communicate with NMD 512 over Bluetooth™(IEEE 802.15), and communicate with PBD 534 over another local areanetwork. In another example, NMD 514 may communicate with CR 522 overanother local area network, and communicate with PBD 536 over Bluetooth.In a further example, each of the PBDs 532, 534, 536, and 538 maycommunicate with each other according to a spanning tree protocol over alocal playback network, while each communicating with CR 522 over alocal area network, different from the local playback network. Otherexamples are also possible.

In some cases, communication means between the NMDs 512, 514, and 516,CR 522, and PBDs 532, 534, 536, and 538 may change depending on types ofcommunication between the devices, network conditions, and/or latencydemands. For instance, communication means 546 may be used when NMD 516is first introduced to the household with the PBDs 532, 534, 536, and538. In one case, the NMD 516 may transmit identification informationcorresponding to the NMD 516 to PBD 538 via NFC, and PBD 538 may inresponse, transmit local area network information to NMD 516 via NFC (orsome other form of communication). However, once NMD 516 has beenconfigured within the household, communication means between NMD 516 andPBD 538 may change. For instance, NMD 516 may subsequently communicatewith PBD 538 via communication path 542, the cloud network 502, andcommunication path 544. In another example, the NMDs and PBDs may nevercommunicate via local communications means 546. In a further example,the NMDs and PBDs may communicate primarily via local communicationsmeans 546. Other examples are also possible.

In an illustrative example, NMDs 512, 514, and 516 may be configured toreceive voice inputs to control PBDs 532, 534, 536, and 538. Theavailable control commands may include any media playback systemcontrols previously discussed, such as playback volume control, playbacktransport controls, music source selection, and grouping, among otherpossibilities. In one instance, NMD 512 may receive a voice input tocontrol one or more of the PBDs 532, 534, 536, and 538. In response toreceiving the voice input, NMD 512 may transmit via communication path542, the voice input to computing device 504 for processing. In oneexample, the computing device 504 may convert the voice input to anequivalent text command, and parse the text command to identify acommand. Computing device 504 may then subsequently transmit the textcommand to the computing device 506. In another example, the computingdevice 504 may convert the voice input to an equivalent text command,and then subsequently transmit the text command to the computing device506. The computing device 506 may then parse the text command toidentify one or more playback commands.

For instance, if the text command is “Play ‘Track 1’ by ‘Artist 1’ from‘Streaming Service 1’ in ‘Zone 1’,” The computing device 506 mayidentify (i) a URL for “Track 1” by “Artist 1” available from “StreamingService 1,” and (ii) at least one playback device in “Zone 1.” In thisexample, the URL for “Track 1” by “Artist 1” from “Streaming Service 1”may be a URL pointing to computing device 508, and “Zone 1” may be thebonded zone 530. As such, upon identifying the URL and one or both ofPBDs 536 and 538, the computing device 506 may transmit viacommunication path 544 to one or both of PBDs 536 and 538, theidentified URL for playback. One or both of PBDs 536 and 538 mayresponsively retrieve audio content from the computing device 508according to the received URL, and begin playing “Track 1” by “Artist 1”from “Streaming Service 1.”

One having ordinary skill in the art will appreciate that the above isjust one illustrative example, and that other implementations are alsopossible. In one case, operations performed by one or more of theplurality of devices 500, as described above, may be performed by one ormore other devices in the plurality of device 500. For instance, theconversion from voice input to the text command may be alternatively,partially, or wholly performed by another device or devices, such as NMD512, computing device 506, PBD 536, and/or PBD 538. Analogously, theidentification of the URL may be alternatively, partially, or whollyperformed by another device or devices, such as NMD 512, computingdevice 504, PBD 536, and/or PBD 538.

f. Example Network Microphone Device

FIG. 6 shows a function block diagram of an example network microphonedevice 600 that may be configured to be one or more of NMDs 512, 514,and 516 of FIG. 5. As shown, the network microphone device 600 includesa processor 602, memory 604, a microphone array 606, a network interface608, a user interface 610, software components 612, and speaker(s) 614.One having ordinary skill in the art will appreciate that other networkmicrophone device configurations and arrangements are also possible. Forinstance, network microphone devices may alternatively exclude thespeaker(s) 614, or have a single microphone instead of a microphonearray 606.

The processor 602 may include one or more processors and/or controllers,which may take the form of a general or special-purpose processor orcontroller. For instance, the processing unit 602 may includemicroprocessors, microcontrollers, application-specific integratedcircuits, digital signal processors, and the like. The memory 604 may bedata storage that can be loaded with one or more of the softwarecomponents executable by the processor 602 to perform those functions.Accordingly, memory 604 may comprise one or more non-transitorycomputer-readable storage mediums, examples of which may includevolatile storage mediums such as random access memory, registers, cache,etc. and non-volatile storage mediums such as read-only memory, ahard-disk drive, a solid-state drive, flash memory, and/or anoptical-storage device, among other possibilities.

The microphone array 606 may be a plurality of microphones arranged todetect sound in the environment of the network microphone device 600.Microphone array 606 may include any type of microphone now known orlater developed such as a condenser microphone, electret condensermicrophone, or a dynamic microphone, among other possibilities. In oneexample, the microphone array may be arranged to detect audio from oneor more directions relative to the network microphone device. Themicrophone array 606 may be sensitive to a portion of a frequency range.In one example, a first subset of the microphone array 606 may besensitive to a first frequency range, while a second subset of themicrophone array may be sensitive to a second frequency range. Themicrophone array 606 may further be arranged to capture locationinformation of an audio source (e.g., voice, audible sound) and/or toassist in filtering background noise. Notably, in some embodiments themicrophone array may consist of only a single microphone, rather than aplurality of microphones.

The network interface 608 may be configured to facilitate wirelessand/or wired communication between various network devices, such as, inreference to FIG. 5, CR 522, PBDs 532-538, computing device 504-508 incloud network 502, and other network microphone devices, among otherpossibilities. As such, network interface 608 may take any suitable formfor carrying out these functions, examples of which may include anEthernet interface, a serial bus interface (e.g., FireWire, USB 2.0,etc.), a chipset and antenna adapted to facilitate wirelesscommunication, and/or any other interface that provides for wired and/orwireless communication. In one example, the network interface 608 may bebased on an industry standard (e.g., infrared, radio, wired standardsincluding IEEE 802.3, wireless standards including IEEE 802.11a,802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communicationstandard, and so on).

The user interface 610 of the network microphone device 600 may beconfigured to facilitate user interactions with the network microphonedevice. In one example, the user interface 608 may include one or moreof physical buttons, graphical interfaces provided on touch sensitivescreen(s) and/or surface(s), among other possibilities, for a user todirectly provide input to the network microphone device 600. The userinterface 610 may further include one or more of lights and thespeaker(s) 614 to provide visual and/or audio feedback to a user. In oneexample, the network microphone device 600 may further be configured toplayback audio content via the speaker(s) 614.

III. Default Playback Device(s)

As discussed above, embodiments described herein may involvedesignations of default playback devices in a media playback system, andapplication of such designations. FIG. 7 shows an example flow diagram700 for designating default playback device(s), and FIG. 9 shows anexample flow diagram 900 for applying default playback devicedesignation(s). Methods 700 and 900 shown present embodiments of methodsthat can be implemented within an operating environment involving, forexample, the media playback system 100 of FIG. 1, one or more of theplayback device 200 of FIG. 2, one or more of the control device 300 ofFIG. 3, and one or more of the plurality of devices of FIG. 5. Methods700 and 900 may include one or more operations, functions, or actions asillustrated by one or more of blocks 702-708 and blocks 902-908,respectively. Although the blocks are illustrated in sequential order,these blocks may also be performed in parallel, and/or in a differentorder than those described herein. Also, the various blocks may becombined into fewer blocks, divided into additional blocks, and/orremoved based upon the desired implementation.

In addition, for methods 700 and 900 and other processes and methodsdisclosed herein, the flowchart shows functionality and operation of onepossible implementation of present embodiments. In this regard, eachblock may represent a module, a segment, or a portion of program code,which includes one or more instructions executable by a processor forimplementing specific logical functions or steps in the process. Theprogram code may be stored on any type of computer readable medium, forexample, such as a storage device including a disk or hard drive. Thecomputer readable medium may include non-transitory computer readablemedium, for example, such as computer-readable media that stores datafor short periods of time like register memory, processor cache andRandom Access Memory (RAM). The computer readable medium may alsoinclude non-transitory media, such as secondary or persistent long termstorage, like read only memory (ROM), optical or magnetic disks,compact-disc read only memory (CD-ROM), for example. The computerreadable media may also be any other volatile or non-volatile storagesystems. The computer readable medium may be considered a computerreadable storage medium, for example, or a tangible storage device. Inaddition, for the method 500 and other processes and methods disclosedherein, each block in FIGS. 6 and 7 may represent circuitry that iswired to perform the specific logical functions in the process.

a. Default Playback Device Designation(s)

Designation of default playback devices in a media playback system mayinvolve assigning a network microphone device to one or more playbackdevices in the media playback system, such that the one or more playbackdevices become the designated default playback devices for functionsassociated with the network microphone device.

As shown in FIG. 7, the method 700 involves determining that a networkmicrophone device is available for assignment at block 702, displaying aprompt to indicate at least one playback zone which the networkmicrophone is to be assigned at block 704, receiving an input indicatinga particular playback zone in the media playback system to which thenetwork microphone device is to be assigned at block 706, and storingdata indicating an assignment of the network microphone device to theparticular playback zone at block 708.

For illustration purposes, method 700 may be performed by CR 522 of FIG.5, which may be one of one or more controller devices configured tocontrol a media playback system including one or more of PBDs 532, 534,536, 538, or other playback devices. Nevertheless, one having ordinaryskill in the art will appreciate that functions discussed in relation tomethod 700 may be additionally or alternatively wholly or partiallyperformed, with or without applicable modifications, by one or moreother devices in the plurality of devices 500 shown in FIG. 5.

In an example scenario of a user interacting with a computing deviceexecuting method 700, such as CR 522, the user of CR 522 may indicatethat a network microphone device is to be assigned to one or moreplayback zones. In response to the indication by the user, CR 522 maydetermine whether one or more network microphone devices are availablefor assignment. In one case, the user may enter into CR 522identification information for a network microphone device the userwishes to assign. In another case for which additional discussion isprovided below, CR 522 may seek within communicative range of CR 522,network microphone devices that are available for assignment. In oneinstance, CR 522 may display a list of found network microphone devices,and prompt the user to select a network microphone device forassignment. Other examples are also possible.

At block 702, method 700 involves determining that a networkedmicrophone device is available for assignment to one or more playbackzones within a local playback network. In discussions herein, playbackdevices and controllers on the local playback network may form a mediaplayback system such as that described in the sections above. Forillustration purposes, the networked microphone device may be NMD 512 ofFIG. 5. Determining that NMD 512 is available for assignment may involvedetermining that NMD 512 is capable of communication with the localplayback network, either as a part of the local area network, or via adevice in the local playback network. As discussed previously, CR 522,and PBDs 532, 534, 536, and 538 (also referred to herein as “householddevices”) may be configured to communicate with each other over a localplayback network. As such, determining that NMD 512 is capable ofcommunication with the local playback network may involve determiningthat NMD 512 is capable of communication with at least one of thehousehold devices. In one case, one or more of the household devices maybe configured to transmit and/or detect from others of the householddevices, messages indicating a presence of the transmitting device onthe local network. Such messages may be transmitted when thetransmitting device is first powered up, periodically, and/or inresponse to requests from other devices. In this case, determining thatNMD 512 is capable of communication with at least one of the householddevices may involve receiving by one or more of the household devicesfrom NMD 512 a message indicating a presence of NMD 512.

In one example, CR 522 may establish communication with NMD 512 over asecond network different from the local playback network. For instance,NMD 512 may establish communication to a local area network (LAN) thatCR 522 is also configured to communicate over, or establishcommunication with CR 522 over a personal area network (PAN). In oneexample, the LAN and/or PAN may be facilitated according to a Bluetooth™(IEEE 802.15) wireless technology standard. In one case, uponestablishing the connection over the second network, NMD 512 maytransmit to CR 522, a message indicating that NMD 512 is available forassignment to one or more playback zones in the local playback network.

In another example, determining that NMD 512 is available for assignmentmay further involve NMD 512 joining the local playback network of thehousehold devices. In one case, communication between CR 522 (or anyother of the household devices) and NMD 512 may be established over asecond network, as discussed previously. In this case, however, CR 522may then transmit over the second network to NMD 512, data indicatingparameters for joining the local playback network. Examples ofparameters for joining the local playback network may include one ormore of a service set identifier (SSID), network encryption type(s),network passwords, network authorization tokens, and networkcommunication channel definitions, among other possibilities. In oneinstance, CR 522 may determine that NMD 512 is available for assignmentafter receiving from NMD 512, acknowledgment of receipt of the networkparameters and/or a message indicating NMD 512 is available forassignment over the second network. In another instance, CR 522 maydetermine that NMD 512 is available for assignment after receiving amessage from the NMD 512 over the local playback network. In thisinstance, the message from the NMD 512 over the local playback networkmay or may not explicitly indicate that NMD 512 is available forassignment because the communication between CR 522 and NMD 512 over thelocal playback network may be sufficient to indicate that NMD 512 isavailable for assignment.

As indicated previously, one or more of NMDs 512, 514, and 516 may bemodules or subcomponents of one or more of the household devices CR 522,and PBDs 532, 534, 536, and 538. In such cases, continuing with theexample above, CR 522 may determine that NMD 512 is available forassignment by identifying the presence of NMD 512 as a subcomponent ofitself (in the case NMD 512 is a module of CR 522), or by determiningthat NMD 512 is a subcomponent of another one of the household devices.In one instance, if NMD 512 is a subcomponent of PBD 532, CR 522 mayidentify NMD 512 and determine that NMD 512 is available for assignmentwhen CR 522 and PBD 532 establish communication (i.e. over the localplayback network). Other examples are also possible.

Once CR 522 determines that NMD 512 is available for assignment, CR 522may provide an indication on a user interface of CR 522, that NMD 512 isavailable for assignment. For illustration purposes, FIG. 8A-D showexample interfaces 802-862 that may be involved when assigning networkmicrophone devices. Interface 802 of FIG. 8A shows a representations ofplayback zones in the local playback network. In one example, aselection (e.g. screen tap, force touch, and/or right click, etc.) of arepresentation corresponding a particular playback zone (in this case,the Office playback zone) may cause the interface to display a menu 804(and/or a series of submenus) that provide representations of actionsthat can be performed on the selected playback zone. As shown, aselection 806 to “Assign Microphone” may be detected. In one example,interface 802 may be displayed and the selection 806 may be receivedprior to CR 522 determining that NMD 512 is available for assignment. Inanother example, interface 802 may be displayed and the selection 806may be received after CR 522 has already determined that NMD 512 isavailable for assignment. In this case, the option to “AssignMicrophone” may not be displayed in the menu 804, or may be grayed-outunless CR 522 has already determined that NMD 512, or at least one othernetwork microphone device is available for assignment. Other examplesare also possible.

Interface 822 of FIG. 8B shows a message box 824 that indicates one ormore network microphone devices have been detected (and available forassignment). The message box 824 may further include selectablerepresentations of network microphone device that are available forassignment. For instance, representation 826 may be selectable toproceed with assigning NMD 512. In one example, interface 822 may beprovided in response to the selection 806 of interface 802. In anotherexample, interface 822 may be provided in response to CR 522 determiningthat NMD 512 (and in this example, NMD 514) are available forassignment. In one case, if interface 822 and message box 824 wereprovided in response to only a detection of one or more networkmicrophone devices, and not from a prior input via the interface toassign a microphone (interface 802), the message box 824 may alsoinclude a selectable option (not shown) to assign the detected networkmicrophone device(s) at a later time. Other examples are also possible.

At block 704, method 700 involves displaying a prompt to indicate atleast one playback zone to which the network microphone device is to beassigned. In some cases, the at least one playback zone, may include twoor more playback devices (such as the bonded zone 530 of FIG. 5, whichincludes PBDs 536 and 538). In such cases, CR 522 may also display aprompt to indicate at least one playback device within the at least oneplayback zone to which NMD 512 is to be assigned. In some other cases,CR 522 may not prompt a selection of a playback device within the atleast one zone. In such cases, NMD 512 may be assigned to each playbackdevice in the bonded zone, or by default, a group coordinator of thebonded zone. Other examples are also possible.

In one embodiment, the prompt to indicate at least one playback zone mayinvolve prompting action physically related to the at least one playbackzone. In one example, the prompt may be for the user to press a buttonon a playback device in the playback zone the user wishes to assign NMD512 to. Interface 842 of FIG. 8C shows an example message box 844 toprompt the user to press a button on a playback device in the playbackzone the user wishes to assign NMD 512. As indicated above, interface842 may be provided in response to a selection of representation 826 oninterface 822. In another example, the prompt may be for the user to tapCR 522 on a playback device in the playback zone the user wishes toassign NMD 512 to. In this case, the playback device may detect CR 522over a near field communication (NFC) protocol.

In such examples where an action physically related to the at least oneplayback zone is involved, indication of the at least one playbackdevice within the at least one playback zone to which NMD 512 is to beassigned may be inherent to the indication of the at least one playbackzone. In other words, the playback device in the at least one playbackzone on which the button press or CR 522 tap occurs may also be theplayback device to which NMD 512 is to be assigned. Other examples arealso possible.

In another embodiment, the prompt to indicate at least one playback zonemay involve prompting action on the user interface of CR 522. In oneexample, CR 522 may display on the interface, for each playback zone inthe local playback network, a corresponding representation (similar tothe playback zone region 420 of FIG. 4), and further display on theinterface, a prompt to select a representation corresponding to theplayback zone to which NMD 512 is to be assigned. Interface 862 of FIG.8D shows an example message box 864 that includes selectablerepresentations corresponding to the playback zones in the localplayback network. As indicated above, interface 862 may be provided inresponse to a selection of representation 826 on interface 822. In thisexample, if the selected representation corresponds to a bonded playbackzone, such as the bonded zone 530, CR 522 may further display on theinterface, a prompt to indicate a particular playback device (i.e. PBDs536 or 538) in the bonded playback zone. For instance, CR 522 maydisplay on the interface a prompt to select a correspondingrepresentation for each playback device in the selected playback zone.

In a further embodiment, the prompt to indicate at least one playbackzone may involve some combination of the action physically related tothe at least one playback zone, and the action on the user interface ofCR 522. For instance, the prompt to indicate a playback zone to whichNMD 512 is to be assigned may involve only action on the user interfaceof CR 522, but a subsequent prompt to indicate a playback device withinthe playback zone may involve actions physically related to the playbackdevice to which NMD 512 is to be assigned. Other examples are alsopossible.

In yet a further embodiment, the prompt to indicate at least oneplayback zone may further include a suggested at least one playbackzone. In one example, CR 522 may identify (i) that NMD 512 was given aname including “Master Bedroom,” and (ii) that a playback zone in thelocal playback network has also been given the name “Master Bedroom,”and accordingly include with, or add to the prompt to indicate at leastone playback zone, a suggestion that the Master Bedroom playback zonemay be a suitable playback zone to which NMD 512 may be assigned. Otherexamples are also possible.

At block 706, method 700 involves receiving an input indicating aparticular playback zone in the local playback network to which thenetwork microphone device is to be assigned. As suggested above, if theparticular includes two or more playback devices, the input may furtherindicate a particular playback device in the particular playback zone.

In one embodiment, if the prompt displayed at block 704 involved anaction physically related to the playback zone, the input indicating theparticular playback zone may be received from a playback device in theparticular playback zone. For instance, if a button on PBD 536 waspressed or a tap on PBD 536 by CR 522 was performed in response to thedisplayed prompt at block 704, PBD 536 may transmit a message to CR 522indicating that PBD 536 and/or bonded zone 530 was selected.

In another embodiment, if the prompt displayed at block 704 involved anaction on the interface of CR 522, the input indicating the particularplayback zone may be received in the form of the selection input(s) bythe user on the interface. Other examples are also possible.

At block 708, method 700 involves storing data indicating an assignmentof the network microphone device to the particular playback zone. In oneexample, continuing with the examples above, storing the data indicatingthe assignment of NMD 512 to the bonded zone 530 may involve storing ona local memory storage of CR 522, the data indicating the assignment. Inanother example, storing the data indicating the assignment may involvetransmitting to one or more of the other household devices, the dataindicating the assignment and a message to cause the one or more of theother household devices to store the data. In yet another example,storing the data indicating the assignment may involve transmitting to aserver, such as one or more of the computing device 504, 506, and 508 ofcloud network 502, the data indicating the assignment and a message tocause the one or more of the computing device 504, 506, and 508 of cloudnetwork 502 to store the data. Other examples re also possible.

As mentioned above, assignment of a network microphone device to aparticular playback zone may also involve an assignment of the networkmicrophone device to at least one playback device in the particularplayback zone. As such, the data indicating the assignment of NMD 512 tothe bonded zone 530 may include data indicating an assignment of NMD 512to PBD 536, if continuing with the examples above. In some cases, if aplayback device in a playback zone is not explicitly indicated, thenetwork microphone device may be assigned to each playback device in theparticular playback zone. In other cases, if a playback device in aplayback zone is not explicitly indicated, a playback device in theparticular playback zone may be automatically and/or intelligentlyidentified, and the network microphone may be assigned to to theidentified playback device. For instance, if the playback zone is abonded zone, a coordinating playback device of the bonded zone may beidentified. In another instance, if the playback zone is a zone group, agroup coordinator playback device in the zone group may be identified.Other examples are also possible.

In one embodiment, the network microphone device that has been assignedmay correspond to one or more unique identifiers. For instance, thenetwork microphone device may have a unique serial number, or acorresponding MAC address, among other possibilities. Accordingly,storing data indicating the assignment of the NMD 512 to the bonded zone530 (and/or PBD 536) may involve storing an assignment of the uniqueidentifier of NMD 512 to the bonded zone 530 (and/or PBD 536).

In one example, CR 522 may receive a unique identifier for NMD 512 wheninitially determining that NMD 512 is available for assignment. In somecases, if the network microphone device did not provide a uniqueidentifier, a unique identifier may be generated and assigned to thenetwork microphone device. Other examples are also possible.

In some embodiments, a network microphone device may be assigned to twoor more playback zones. For instance, in a household with an “open floorplan” such as that shown in FIG. 1, a network microphone device may bepositioned somewhere within the vicinity of the Living Room, DiningRoom, and Kitchen. In such cases, assignment of the network microphonedevice to two or more playback zones may be beneficial.

In one example, continuing with the examples above, CR 522 may displayon the interface, a prompt to indicate a second playback zone to whichNMD 512 is to be assigned, receive an input indicating a second playbackzone in the media playback system, and storing data indicating anassignment of the network microphone device to the second playback zonesuch that the network microphone device is assigned to both the firstplayback zone and the second playback zone, similar to blocks 704-708.

In one example, interactions to assign NMD 512 to the second playbackzone may be performed in series. For instance, CR 522 may display on theinterface after receiving the input indicating that NMD 512 is to beassigned to bonded zone 530 at block 706, or after storing dataindicating the assignment of NMD 512 to bonded zone 530, a prompt toindicate a second playback zone to which NMD 512 is to be assigned.

In another example, interactions to assign NMD 512 to the secondplayback zone may be performed substantially in parallel with theinteractions to assign NMD 512 to the bonded zone 530. For instance, theprompt to indicate at least one playback zone at block 704 may be aprompt to indicate each playback zone to which NMD 512 is to beassigned. In this case, if the input received at block 706 indicatesonly a single playback zone, then the data stored at block 708 mayindicate an assignment of NMD 512 to only the single playback zone. Onthe other hand, if the input received at block 706 indicates two or moreplayback zones, the data stored at block 708 may indicate an assignmentof NMD 512 to each of the two or more playback zones.

In a further example, the prompt to indicate a playback zone may promptthe user to group together the two or more playback zones to which NMD512 is to be assigned, such that the user can then select on theinterface from among a representation of zones, a representationcorresponding to the group (or alternatively, physically select aplayback device in the zone group) to indicate that NMD 512 is to beassigned to the zone group and/or playback zones in the zone group.Other examples are also possible.

TABLE 1 PBD in Playback NMD Playback Zone 1 Zone 1 Zone 2 PBD in Zone 2NMD 512 Master Bedroom PBD 536 n/a n/a NMD 514 Living Room PBD 534Kitchen n/a NMD 516 Office PBD 532 Master PBD 536 Bedroom PBD 538

For illustration purposes, Table 1 shows an example set of entries in adefault playback device database. As shown, Table 1 lists each of theNMDs 512, 514, and 516, and the playback zone(s) and playback device(s)to which they are assigned. In this example, both NMD 512 and NMD 516are assigned to the Master Bedroom playback zone (bonded zone 530). Inthis example however, NMD 512 is further assigned specifically to PBD536 of the Master Bedroom playback zone, while NMD 516 is furtherassigned specifically to both PBD 536 and PBD 538. Further in thisexample, NMD 514 is assigned to both the Living Room playback zone andthe Kitchen playback zone. However, NMD 514 is further assigned to PBD534 in the Living Room playback zone, but not further assigned to anyplayback device in the Kitchen playback zone.

One having ordinary skill in the art will appreciate that differentformatting, organization, and sets of parameters may also be possible toachieve similar functions as Table 1. In one example, two or morenetwork microphone devices may be assigned to a single playback zone orplayback device. In another example, each network microphone device maybe assigned to three or more playback zones. In a further example, eachnetwork microphone device may be assigned to one or more playbackdevices, and not any playback zones. In yet another example, Table 1 maylist each playback zone and/or playback device in the local playbacknetwork, of which perhaps not every listed playback zone(s) or playbackdevice(s) has assigned thereto, one or more network microphone devices.Other examples are also possible.

While the above discussions may generally refer to assignments of one ormore network microphone devices to one or more playback zones and/orplayback devices, one having ordinary skill in the art will appreciatethat such assignments and designations may be additionally oralternatively established according to other methods and/or protocols.For instance, one or more playback zones and/or playback devices mayequivalently or alternatively be assigned to one or more networkmicrophone devices, and corresponding data may be stored locally at theone or more network microphone devices or remotely at a server such ascomputing device 504. Continuing with the example of Table 1, entries inTable 1 may alternatively (or additionally) be provided based onassignments of PBD 536 and/or the Master Bedroom playback zone to NMD512 via an interface corresponding to at least NMD 512 (i.e. acontroller interface for managing and controlling at least NMD 512).Similarly, the Office playback zone and the Master Bedroom playback zonemay both be assigned to NMD 516 via the interface corresponding to atleast NMD 512 and 516.

In addition, both forms of assignments and designations may co-existsuch that the plurality of network microphone devices and the pluralityof playback devices may be cross-assigned to each other. In such a case,the cross-assignments may or may not fully match. For instance, in somecases, a network microphone device may be assigned to two playbackdevices, but only one or neither of the playback devices are assigned tothe network microphone. Other examples are also possible.

As indicated above, assignment of the network microphone device to theparticular playback zone indicates that the particular playback zone isdesignated as a default playback zone for the network microphone device.The following section provides examples for applications of such adefault playback zone designation.

b. Application of Default Playback Device Designation(s)

As shown in FIG. 9, the method 900 involves maintaining a databasecomprising data indicating an assignment of an identification of anetwork microphone device to a playback zone at block 902, receiving amessage indicating (i) the identification of the network microphonedevice and (ii) a media playback command at block 904, identifying theplayback zone in the media playback system based on the data in thedatabase and the received message at block 906, and transmitting to theplayback zone, a message indicating the playback command at block 908.

For illustration purposes, method 900 may be performed by computingdevice 506 of FIG. 5. Nevertheless, one having ordinary skill in the artwill appreciate that functions discussed in relation to method 900 maybe wholly or partially performed, with or without applicablemodifications, by one or more other devices in the plurality of devices500 shown in FIG. 5. For instance, the method 900 may be wholly orpartially performed by the computing devices 504 and/or 508, or thecloud network 502.

At block 902, the method 900 involves maintaining a database comprisingdata indicating an assignment of an identification of a networkmicrophone device to a playback zone of a media playback system. In oneexample, maintaining the database may involve functions similar to thatdescribed above in connection to method 700 of FIG. 7. In addition,maintaining the database may further involve updating the database inresponse to changes to the media playback system and/or local playbacknetwork. For instance, if a network microphone device has beenreassigned to different playback zone(s) and/or playback device(s), thedatabase may be updated. Likewise, if one or more devices, includingnetwork microphone devices such as NMDs 512, 514, and 516, playbackdevices such as PBDs 532, 534, 536, and 538, or control devices, such asCR 552 are added, removed, temporarily disconnected, or reconnected, thedatabase may be updated accordingly. Other examples of maintaining thedatabase are also possible.

At block 904, the method 900 involves receiving a message indicating (i)the identification of the network microphone device and (ii) a mediaplayback command. Continuing with the examples above, computing device506 may receive the message from the NMD 514.

In one example, computing device 506 may receive the message from NMD514 via computing device 504. As discussed in connection to FIG. 5, NMD514 may transmit a voice input to computing device 504 via communicationpath 542, and computing device 504 may convert the voice input to anequivalent text command, and subsequently transmit the text command tothe computing device 506. In such a case, the message indicating (i) theidentification of the network microphone device and (ii) the mediaplayback command may include the text command from the computing device504.

In another example, computing device 506 may receive the messagedirectly from NMD 514. In such a case, the message may include dataindicating the media playback command, while the source of the messageidentified in the message (i.e. within a data packet header/prefix ofthe message) may indicate NMD 514. In this case, the computing device506 may also process and convert the voice input to an equivalent textcommand.

At block 906, the method 900 involves identifying the playback zone inthe media playback system based on the data in the database and thereceived message. As also discussed in connection to FIG. 5, thecomputing device 506 may then parse the text command to identify one ormore playback commands. During the parsing of the text command toidentify one or more playback commands, the computing device 506 mayidentify a particular command, but may determine that a playback zone toperform the particular command was not identified. In one example,computing device 506 may determine that a playback zone to perform theparticular command was not identified if no zone indication was providedin the playback command. In another example, computing device 506 maydetermine that a playback zone to perform the particular command was notidentified if a zone indication that was provided in the playbackcommand does not exist in the media playback system. Other examples arealso possible.

Whichever the case, in response to the determining that the receivedmessage does not indicate a particular playback zone, computing device906 may identify in the database, a playback zone in the media playbacksystem based on the identification of the network microphone device inthe received message. In other words, computing device 506 may identifya playback zone designated as the default playback zone of the networkmicrophone device identified in the received message (and/or from whichthe media playback command originated.)

Continuing with the examples above, including Table 1, if the receivedmessage does not identify a valid playback zone but indicates NMD 512,then computing device 506 may identify the playback zone “MasterBedroom” and/or PBD 536 as the playback zone to perform the mediaplayback command in the received message.

As shown in Table 1, in some cases, a network microphone device such asNMD 514 or 516 may be assigned to two or more playback zones (and/orplayback devices). In one example, computing device 506 may identifyeach of the two or more playback zones as playback zones that are toperform the media playback command. For instance, if the receivedmessage indicates NMD 514, computing device 506 may identify both theLiving Room and the Kitchen as playback zones that are to perform themedia playback command.

In another example, computing device 506 may identify a subset of thetwo or more playback zones as playback zones that are to perform themedia playback command. For instance, if the received message indicatesNMD 516, computing device may identify one of the Office or the MasterBedroom as the playback zone that is to perform the media playbackcommand. In some cases, computing device 506 may identify the subsetbased on additional information, such as contextual information.

In one case, computing device 506 may identify the subset of the two ormore playback zones as playback zones that are to perform the mediaplayback command based on media content associated with the two or moreplayback zones. For instance, if a first subset of the two or moreplayback zones is playing media content and/or is associated with mediacontent (i.e. has media content in a corresponding playback queue) whilea second subset of the two or more playback zones is not playing mediacontent and/or is not associated with media content when the voice inputwas received at the corresponding network microphone device, computingdevice 506 may identify the first subset of the two or more playbackzones as playback zones that are to perform the media playback command.

Additionally, computing device 506 may identify the subset of the two ormore playback zones based on the media playback command and mediaplayback states of the two or more playback zones. In such a case, thecomputing device 506 may be configured to receive and maintain playbackstates for each of the playback zones in the media playback system. Forinstance, if the media playback command involves pausing playback ofmedia content while a first subset of the two or more playback zones isplaying media content and a second subset of the two or more playbackzones is not playing media content when the voice input was received bythe corresponding network microphone device, then computing device 506may identify the first subset of the two or more playback zones based onan assumption that a user is more likely to provide a pause command to aplayback zone that is playing media content than a playback zone that isnot playing media content (i.e. already paused).

In another case, the database (or another database) may be configured toalso store information relating to media playback history within themedia playback system and/or more specifically, media playback commandhistory associated with each of the network microphone devices. Forinstance, data in the database may indicate that a subset of the two ormore playback zones is more frequently used to play media content and/ormore frequently used to play media content in response to a voicecommand via the corresponding network microphone device. In such a case,computing device 506 may identify the more frequently used subset of twoor more playback zones as playback zones that are to perform the mediaplayback command.

In a further case, the media playback history and/or media playbackcommand history may further indicate a times of day, or days of week,etc. when a subset of the two or more playback zones is more frequentlyused to playback media content and/or more frequently used to play mediacontent in response to a voice command. In such a case, computing device506 may further identify the subset of two or more playback zones thatare to perform the media playback command based on a time when the voiceinput was received at the corresponding network microphone device.

In yet another case, computing device 506 may identify the subset of thetwo or more playback zones as playback zones to perform the mediaplayback command based further on proximity information available to thecomputing device 506. In other words, computing device 506 may identifythe subset of the two or more playback zones based on a physicallocation of the user when providing the voice input to the correspondingnetwork microphone device.

In one example, the voice input detected and processed by the networkmicrophone device may contain directional information corresponding tothe voice input. In one embodiment, during setup and assignment of thenetwork microphone device to the two or more playback zones, the networkmicrophone device may determine and store in memory (locally orremotely, i.e. computing device 504), locations of the two or moreplayback zones in relation to the network microphone device. Forinstance, during setup and assignment of the network microphone device,or over time, the network microphone device may detect playback of mediacontent by the two or more playback zones, and correlate directions fromwhich the playback of media content is detected with the correspondingplayback zones. As such, the physical location of the user may bedetermined based on a direction from which the voice input was detectedby the network microphone device.

In another example, as previously suggested, one or more other devicesin the media playback system may also include network microphone devicesand/or other sensors. Accordingly, a network of available sensors may beconfigured to determine proximity or locate (i.e. via triangulation,etc.) the user when the user provides the voice input to thecorresponding network microphone device. In one case, if the user isholding, or has recently used a control device such as CR 522, alocation of the user, or proximity between the user and the playbackdevices/playback zones may be determined based on a signal strengthbetween the control device and the playback devices. Similarly, an audiomagnitude of the voice input as detected by the other network microphonedevices, or wireless signal interference caused by the user between thevarious devices may also be received and applied by computing device 506to determine the physical location of the user when the voice input wasdetected, and accordingly identify the subset of the two or moreplayback zones as playback zones that are to perform the media playbackcommand. Other examples are also possible.

At block 908, the method 900 involves transmitting to the playback zone,a message indicating the media playback command. As describedpreviously, each playback zone in the media playback system includes atleast one playback device. Accordingly, transmitting to the playbackzone, the message indicating the media playback command may involvetransmitting the message indicating the media playback command to thecorresponding at least one playback device of the playback zone.Referring to Table 1 and FIG. 5, the Office playback zone includes justPBD 532. In this case, transmitting a message indicating the mediaplayback command to the Office playback zone may involve computingdevice 506 transmitting the message indicating the media playbackcommand to PBD 532.

Referring again to Table 1 and FIG. 5, the bonded zone 530 (MasterBedroom) includes both PBDs 536 and 538. In one such case, computingdevice 506 may transmit the message indicating the media playbackcommand to both PBDs 536 and 538. In another such case, computing device506 may transmit the message indicating the media playback command toonly one of the playback devices in the playback zone.

In one instance, the computing device 506 may select one of the PBDs 536and 538 according to the database. For example, if the media playbackcommand originated from NMD 512, and computing device 506 istransmitting the message indicating the media playback command to theMaster Bedroom playback zone, computing device 506 may transmit themessage indicating the media playback command to PBD 536 because NMD 512is further assigned to PBD 536, but not to PBD 538.

In another example, if the media playback command originated from NMD516, and computing device 506 is transmitting the message indicating themedia playback command to the Master Bedroom playback zone, computingdevice 506 may select one of PBD 536 or PBD 538 based on additionalinformation because NMD 516 has been assigned to both PBD 536 and PBD538 as part of an assignment to the Master Bedroom playback zone. In onecase, computing device 506 may select one of PBD 536 or PBD 538 based onone or more factors, such as device processing power and networkconditions, among other possibilities. Additionally, or alternatively,computing device 506 may select one of PBD 536 or PBD 538 based on oneof the playback devices being a coordinator for the bonded zone. Otherexamples are also possible.

In another case, as previously discussed, computing device 506 mayidentify two or more playback zones as playback zones that are toperform the media playback command. In such a case, computing device 506may transmit the message indicating the media playback command to eachplayback device in each of the two or more playback zones, a subset ofthe playback devices in each of the two or more playback zones, or somecombination thereof.

Further, in a case where all or at least a subset of the two or moreplayback zones identified as playback zones that are to perform themedia playback command are grouped in a zone group, computing device 506may identify a single playback device in the zone group to transmit themessage indicating the media playback command, rather than transmittingthe message to a playback device in each playback zone. In this case,computing device 506 may select a playback device from the zone groupbased on one or more factors, such as device processing power andnetwork condition, among other possibilities. Additionally, oralternatively, computing device 506 may select a playback device fromthe zone group based on the playback device being a group coordinatorfor the zone group. Other examples are also possible.

In one embodiment, after transmitting the message indicating the mediaplayback command to the playback zone(s), computing device 506 mayfurther transmit to the computing device 504 and/or the networkmicrophone device, a message indicating the playback command was sentfor execution in the playback zone. In one example, the computing device506 may receive from at least one playback device in the playback zone,a message indicating that the playback zone is executing the playbackcommand prior to transmitting to the network microphone device, themessage indicating the playback command was sent for execution in theplayback zone.

In one case, computing device 506 may transmit the message indicatingthe playback command was sent for execution in the playback zonedirectly to the network microphone device. In another case, computingdevice 506 may transmit the message indicating the playback command wassent for execution in the playback zone to the network microphone devicevia another computing device, such as computing device 504 within cloudnetwork 502.

In yet another case, computing device 506 may transmit the messageindicating the playback command was sent for execution in the playbackzone to the network microphone device via a playback device in the mediaplayback system. For instance, computing device 506 may transmit themessage indicating that the playback command was sent for execution toPMD 536 via communication path 544, and PMD 536 may relay the message toNMD 512 via local communications means 546.

The playback device relaying the message indicating the playback commandwas sent for execution may be a playback device executing the mediaplayback command. For instance, the computing device 506, whentransmitting to the playback zone, the message indicating the mediaplayback command, may further cause a playback device in the identifiedplayback zone to transmit to the corresponding network microphonedevice, upon receiving the message indicating the media playbackcommand, a message indicating that the media playback command was sentfor execution.

Additionally, or alternatively, the computing device 506 may determinethat the media playback command has been executed, or is being executed,and responsively transmit to computing device 504 and/or the networkmicrophone device, either directly or via another device, a messageindicating that the media playback command has been executed or is beingexecuted.

Further, the computing device 506, when transmitting to the playbackzone, the message indicating the media playback command, may furthercause a playback device in the identified playback one to transmit tothe corresponding network microphone device, upon completing executionor during execution of the media playback command, a message indicatingthat the media playback command has been executed or is being executed.Other examples are also possible.

IV. Conclusion

The description above discloses, among other things, various examplesystems, methods, apparatus, and articles of manufacture including,among other components, firmware and/or software executed on hardware.It is understood that such examples are merely illustrative and shouldnot be considered as limiting. For example, it is contemplated that anyor all of the firmware, hardware, and/or software aspects or componentscan be embodied exclusively in hardware, exclusively in software,exclusively in firmware, or in any combination of hardware, software,and/or firmware. Accordingly, the examples provided are not the onlyway(s) to implement such systems, methods, apparatus, and/or articles ofmanufacture.

As indicated above, the examples provided herein involve designating adefault playback device in a media playback system and applying suchdesignation of the default playback device. In one aspect, a method isprovided. The method involves determining, by a computing device, that anetworked microphone device is available for assignment to one or moreplayback zones within a local playback network, displaying by thecomputing device, a prompt to indicate at least one playback zone towhich the network microphone device is to be assigned, receiving, by thecomputing device, an input indicating a particular playback zone in thelocal playback network to which the network microphone device is to beassigned, and storing, by the computing device, data indicating anassignment of the network microphone device to the particular playbackzone.

In another aspect, a computing device is provided. The computing deviceincludes a processor, and memory having stored thereon instructionsexecutable by the processor to cause the device to perform functions.The functions include determining that a networked microphone device isavailable for assignment to one or more playback zones within a localplayback network, displaying a prompt to indicate at least one playbackzone to which the network microphone device is to be assigned, receivingan input indicating a particular playback zone in the local playbacknetwork to which the network microphone device is to be assigned, andstoring data indicating an assignment of the network microphone deviceto the particular playback zone.

In yet another aspect, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions. The functions include determining that anetworked microphone device is available for assignment to one or moreplayback zones within a local playback network, displaying a prompt toindicate at least one playback zone to which the network microphonedevice is to be assigned, receiving an input indicating a particularplayback zone in the local playback network to which the networkmicrophone device is to be assigned, and storing data indicating anassignment of the network microphone device to the particular playbackzone.

In one aspect, a method is provided. The method maintaining, by acomputing device, a database comprising data indicating an assignment ofan identification of a network microphone device to a playback zone of amedia playback system, receiving, by the computing device, a messageindicating (i) the identification of the network microphone device and(ii) a media playback command, identifying, by the computing device theplayback zone in the media playback system based on the data in thedatabase and the received message, and transmitting, by the computingdevice to the playback zone, a message indicating the media playbackcommand.

In another aspect, a computing device is provided. The computing deviceincludes a processor, and memory having stored thereon instructionsexecutable by the processor to cause the device to perform functions.The functions include maintaining a database comprising data indicatingan assignment of an identification of a network microphone device to aplayback zone of a media playback system, receiving a message indicating(i) the identification of the network microphone device and (ii) a mediaplayback command, identifying the playback zone in the media playbacksystem based on the data in the database and the received message, andtransmitting to the playback zone, a message indicating the mediaplayback command.

In yet another aspect, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions. The functions include maintaining adatabase comprising data indicating an assignment of an identificationof a network microphone device to a playback zone of a media playbacksystem, receiving a message indicating (i) the identification of thenetwork microphone device and (ii) a media playback command, identifyingthe playback zone in the media playback system based on the data in thedatabase and the received message, and transmitting to the playbackzone, a message indicating the media playback command.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of aninvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible,non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on,storing the software and/or firmware.

We claim:
 1. A system comprising a first network device and a secondnetwork device communicatively coupled to the first network device overa network, wherein the first network device comprises a networkmicrophone device, and wherein the second network device comprises aprocessor and memory storing instructions executable by the secondcomputing device to perform functions comprising: determining that thenetwork microphone device is available for assignment to one of aplurality of playback zones within a local playback network; causing acontroller device to display a prompt to select, from the plurality ofplayback zones, at least one playback zone to which the networkmicrophone device is to be assigned; receiving an input indicating aselection of a particular playback zone of the plurality of playbackzones as the at least one playback zone; after receiving the input,assigning the particular playback zone to the network microphone device,wherein the assigning comprises configuring a playback device of the atparticular playback zone to be a default output device in response tovoice inputs received via the network microphone device; and causing tobe stored data indicating an assignment of the network microphone deviceto the particular playback zone.
 2. The system of claim 1, furthercomprising a first playback device and a second playback device, andwherein the particular playback zone comprises the first playbackdevice, and wherein the input indicating the selection of the particularplayback zone comprises an input indicating the first playback device.3. The system of claim 2, wherein the particular playback zone furthercomprises the second playback device.
 4. The system of claim 2, whereinone of the first playback device and second playback device comprisesthe network microphone device.
 5. The system of claim 1, wherein theparticular playback zone comprises two or more playback devices, andwherein the input indicating the selection of the particular playbackzone in the media playback system comprises an input indicating aparticular playback device of the two or more playback devices in theparticular playback zone to be the default output device in response tovoice inputs received via the network microphone device.
 6. The systemof claim 1, wherein determining that a networked microphone device isavailable for assignment to one of a plurality of playback zones withinthe local playback network comprises receiving from the networkmicrophone device, a message indicating that the network microphonedevice is available for assignment to one of the plurality of playbackdevices within the local playback network.
 7. The system of claim 1wherein determining that the network microphone device is available forassignment to one of the plurality of playback zones comprisesdetermining that the first network device is available for assignment toone of the plurality of playback zones.
 8. The system of claim 1,wherein the first network device is coupled to the second network deviceover a wide area network, and wherein the playback network comprises alocal area network.
 9. The system of claim 1, wherein the networkmicrophone device corresponds to a unique identifier, and whereincausing to be stored, data indicating an assignment of the networkmicrophone device to the particular playback zone comprises causing tobe stored data indicating an assignment of the unique identifier to theparticular playback zone.
 10. The system of claim 1, wherein theparticular playback zone is a first playback zone, and wherein thefunctions further comprise: receiving an input indicating a secondplayback zone in the local playback network; and causing to be stored,data indicating an assignment of the network microphone device to thesecond playback zone such that the network microphone device is assignedto both the first playback zone and the second playback zone.
 11. Amethod, comprising: determining that a network microphone device isavailable for assignment to one of a plurality of playback zones withina local playback network; causing a controller device to display aprompt to select, from the plurality of playback zones, at least oneplayback zone to which the network microphone device is to be assigned;receiving an input indicating a selection of a particular playback zoneof the plurality of playback zones as the at least one playback zone;after receiving the input, assigning the particular playback zone to thenetwork microphone device, wherein the assigning comprises configuring aplayback device of the at particular playback zone to be a defaultoutput device in response to voice inputs received via the networkmicrophone device; and causing to be stored data indicating anassignment of the network microphone device to the particular playbackzone.
 12. The method of claim 11, wherein determining that a networkedmicrophone device is available for assignment to one of a plurality ofplayback zones within the local playback network comprises transmittingfrom the network microphone device to a server over a network, a messageindicating that the network microphone device is available forassignment to one of the plurality of playback devices within the localplayback network.
 13. The method of claim 12, wherein the networkcomprises a wide area network.
 14. The method of claim 11, whereindetermining that the network microphone device is available forassignment to one of the plurality of playback zones comprisesdetermining that the first network device is available for assignment toone of the plurality of playback zones.
 15. The method of claim 11,wherein the particular playback zone is a first playback zone, andwherein the method further comprises: receiving an input indicating asecond playback zone in the local playback network; and causing to bestored, data indicating an assignment of the network microphone deviceto the second playback zone such that the network microphone device isassigned to both the first playback zone and the second playback zone.16. A non-transitory computer readable storage medium includinginstructions for execution by a processor, the instructions, whenexecuted, cause the processor to implement a method comprising:determining that a network microphone device is available for assignmentto one of a plurality of playback zones within a local playback network;causing a controller device to display a prompt to select among theplurality of playback zones, a given playback zone to which the networkmicrophone device is to be assigned, wherein assigning the givenplayback zone to the network microphone device comprises configuring aplayback device of the given playback zone to be a default output devicein response to voice inputs received via the network microphone device;receiving an input indicating a selection of a particular playback zoneof the plurality of playback zones; and causing to be stored dataindicating an assignment of the network microphone device to theparticular playback zone.
 17. The non-transitory computer readablestorage medium of claim 16, wherein determining that a networkedmicrophone device is available for assignment to one of a plurality ofplayback zones within the local playback network comprises receivingfrom the network microphone device over a network, a message indicatingthat the network microphone device is available for assignment to one ofthe plurality of playback devices within the local playback network. 18.The non-transitory computer readable storage medium of claim 17, whereinthe network comprises a wide area network.
 19. The non-transitorycomputer readable storage medium of claim 16, wherein determining thatthe network microphone device is available for assignment to one of theplurality of playback zones comprises determining that the first networkdevice is available for assignment to one of the plurality of playbackzones.
 20. The non-transitory computer readable storage medium of claim18, wherein the particular playback zone is a first playback zone, andwherein the functions further comprise: receiving an input indicating asecond playback zone in the local playback network; and causing to bestored, data indicating an assignment of the network microphone deviceto the second playback zone such that the network microphone device isassigned to both the first playback zone and the second playback zone.